Customized hardware selection for a mobile phone

ABSTRACT

A method of customizing hardware by an end user for a mobile phone is provided. The method includes receiving from an end-user a selection of a mobile phone shell from a set of mobile phone shells, sending to the end-user a subset of interchangeable hardware components having different functions, and receiving from the end-user a selection of at least one hardware component from the subset of interchangeable hardware components. The subset of interchangeable hardware components is generated based on a compatibility between the selected mobile phone shell and the set of available interchangeable hardware components.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of the earliest availableeffective filing date(s) from the following listed application(s) (the“Priority Applications”), if any, listed below (e.g., claims earliestavailable priority dates for other than provisional patent applicationsor claims benefits under 35 USC 119(e) for provisional patentapplications, for any and all parent, grandparent, great-grandparent,etc. applications of the Priority Application(s)).

PRIORITY APPLICATIONS

The present application constitutes a continuation of U.S. patentapplication Ser. No. 13/765,497, entitled CUSTOMIZED HARDWARE SELECTIONFOR A MOBILE PHONE, naming Alistair K. Chan, Philip A. Eckhoff, RoderickA. Hyde, Jordin T. Kare, David B. Tuckerman, Lowell L. Wood, Jr. asinventors, filed Feb. 12, 2013, which is currently co-pending or is anapplication of which a currently co-pending application is entitled tothe benefit of the filing date, and which is a continuation of U.S.patent application Ser. No. 13/340,463, Patent No. 8,391,934 entitledCUSTOMIZED HARDWARE SELECTION FOR A MOBILE PHONE, naming Alistair K.Chan, Philip A. Eckhoff, Roderick A. Hyde, Jordin T. Kare, David B.Tuckerman, Lowell L. Wood, Jr. as inventors, filed Dec. 29, 2011.

If an Application Data Sheet (ADS) has been filed on the filing date ofthis application, it is incorporated by reference herein. Anyapplications claimed on the ADS for priority under 35 U.S.C. 119, 120,121, or 365(c), and any and all parent, grandparent, great-grandparent,etc. applications of such applications, are also incorporated byreference, including any priority claims made in those applications andany material incorporated by reference, to the extent such subjectmatter is not inconsistent herewith.

If the listings of applications provided above are inconsistent with thelistings provided via an ADS, it is the intent of the Applicant to claimpriority to each application that appears in the DomesticBenefit/National Stage Information section of the ADS and to eachapplication that appears in the Priority Applications section of thisapplication.

All subject matter of the Priority Applications and of any and allapplications related to the Priority Applications by priority claims(directly or indirectly), including any priority claims made and subjectmatter incorporated by reference therein as of the filing date of theinstant application, is incorporated herein by reference to the extentsuch subject matter is not inconsistent herewith.

BACKGROUND

The present disclosure relates generally to the field of mobile phones.More specifically, the present disclosure relates to the field ofhardware customizable mobile phones.

Mobile phones are notoriously cramped for space, making it difficult toinclude new widgetry with limited, rather than universal, appeal.Traditionally, as the volume required for essential hardware hasdecreased, mobile phones have also gotten smaller. Some new widgets havebeen incorporated into at least some of the freed up space, but tomaintain economies of scale, mobile phones and the accompanying widgetsare generally not customizable. Users may select a desired phone withpreselected widgets, but only from a limited selection offered by themobile phone maker or its competitors. Thus, there is a need for ahardware customizable mobile phone with user selectable components.

SUMMARY

One embodiment relates to a mobile phone. The mobile phone includes ashell and a hardware component coupled to the shell, wherein thehardware component is selected from a set of interchangeable componentshaving substantially the same size but different functions.

Another embodiment relates to a computerized method of customizinghardware for a mobile phone. The method includes receiving shellselection information from a user input device, identifying a set ofhardware components, the set of hardware components generated based on acompatibility between the hardware components and the shell selectioninformation, and outputting the identified set of compatible hardwarecomponents.

Another embodiment relates to a computerized method of customizinghardware for a mobile phone. The method includes receiving a hardwarecomponent selection information from a user input device, identifying aset of compatible mobile phone shells, the set of mobile phone shellsgenerated based on a compatibility between the mobile phone shells andthe hardware component selection information, and outputting theidentified set of compatible mobile phone shells.

Another embodiment relates to a method of customizing hardware by an enduser for a mobile phone. The method includes receiving from an end-usera selection of a mobile phone shell from a set of mobile phone shells,sending to the end-user a subset of interchangeable hardware componentshaving different functions, and receiving from the end-user a selectionof at least one hardware component from the subset of interchangeablehardware components. The subset of interchangeable hardware componentsis generated based on a compatibility between the selected mobile phoneshell and the set of available interchangeable hardware components.

Another embodiment relates to a method of selling a mobile phone. Themethod includes offering to sell a hardware customizable mobile phonewith one or more selectable hardware components configured to fit withina shell, offering a plurality of selectable options for at least onehardware component configured to fit within the shell, and receiving aselection of at least one hardware component configured to fit withinthe shell.

Another embodiment relates to a method of customizing hardware for amobile phone. The method includes selecting a mobile phone shell from aset of mobile phone shells, and selecting at least one hardwarecomponent from a subset of interchangeable hardware components havingdifferent functions, the subset of interchangeable hardware componentsgenerated based on a compatibility between the selected mobile phoneshell and the set of available interchangeable hardware components.

The foregoing is a summary and thus by necessity containssimplifications, generalizations and omissions of detail. Consequently,those skilled in the art will appreciate that the summary isillustrative only and is not intended to be in any way limiting. Otheraspects, inventive features, and advantages of the devices and processesdescribed herein, as defined solely by the claims, will become apparentin the detailed description set forth herein and taken in conjunctionwith the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an exemplary display showing a variety of mobile phones, shownaccording to various exemplary embodiments.

FIGS. 2A-2C are schematic block diagrams of mobile phones, shownaccording to exemplary embodiments.

FIG. 3 is a schematic block diagram of a mobile phone, shown accordingto another embodiment.

FIGS. 4A-4D are detailed schematic block diagrams of cross-sectionalside-elevation views of mobile phones, shown according to an exemplaryembodiment.

FIG. 5 is an exemplary display showing a list of mobile phone shells,shown according to an exemplary embodiment.

FIG. 6 is an exemplary display showing a list of hardware components,shown according to an exemplary embodiment.

FIG. 7 is an exemplary display showing images of a mobile phone shelland hardware components, shown according to an exemplary embodiment.

FIG. 8 is a schematic diagram of a server and a client, connected over anetwork and configured for using the systems and methods of thisdisclosure, shown according to an exemplary embodiment.

FIG. 9 is a detailed block diagram of processing electronics, shownaccording to an exemplary embodiment.

FIG. 10 is a flowchart of a process for customizing hardware for amobile phone, shown according to an exemplary embodiment.

FIG. 11 is a flowchart of a process for customizing hardware for amobile phone, shown according to another embodiment.

FIG. 12 is a flowchart of a process for customizing hardware for amobile phone, shown according to another embodiment.

FIG. 13 is a flowchart of a process for customizing hardware for amobile phone, shown according to another embodiment.

FIG. 14 is a flowchart of a process for customizing hardware for amobile phone, shown according to another embodiment.

FIG. 15 is a flowchart of a process for customizing hardware for amobile phone, shown according to another embodiment.

FIG. 16 is a flowchart of a process for customizing hardware for amobile phone, shown according to another embodiment.

FIG. 17 is a flowchart of a process for customizing hardware for amobile phone, shown according to another embodiment.

FIG. 18 is a flowchart of a process for customizing hardware for amobile phone, shown according to another embodiment.

FIG. 19 is a flowchart of a process for customizing hardware for amobile phone, shown according to another embodiment.

FIG. 20 is a flowchart of a process for customizing hardware for amobile phone, shown according to another embodiment.

FIG. 21 is a flowchart of a process for selling a mobile phone, shownaccording to an exemplary embodiment.

FIG. 22 is a flowchart of a process for selling a mobile phone, shownaccording to another embodiment.

FIG. 23 is a flowchart of a process for selling a mobile phone, shownaccording to another embodiment.

FIG. 24 is a flowchart of a process for customizing hardware for amobile phone, shown according to another embodiment.

FIG. 25 is a flowchart of a process for customizing hardware for amobile phone, shown according to another embodiment.

DETAILED DESCRIPTION

Referring generally to the figures, systems and methods for a hardwarecustomizable mobile phone and components thereof are shown according tovarious exemplary embodiments. A hardware customizable mobile phonegenerally includes a shell and one or more selectable hardwarecomponents coupled to the shell, either directly or indirectly (e.g.,via a circuit board). For example, the selectable hardware component mayplug into a receiver located in the phone. The selectable hardwarecomponents may come from a set of components having substantially thesame size, but different functions. The selectable hardware componentsmay be interchangeable with other hardware components from the same setor from a second set of components. The second set of components mayhave the same or different function and a different size, yet still becompatible with the receiver and the size of the shell. Methods ofcustomizing a mobile phone are also described. According to oneembodiment, a user may select a shell from a set of available mobilephone shells or select a hardware component from a set of availablehardware components. The user is then provided with a subset of mobilephone shells or a subset of hardware components that are compatible withthe selected shell or component. Compatibility may be based on a sizevalue (e.g., length, width, thickness, area, volume, etc.), shape of thehardware component, power consumption, or receiver availability of theshell or other components. The user may then continue to select a shellor additional hardware components to further customize the mobile phone.

It should further be noted that for purposes of this disclosure, theterm coupled means the joining of two members directly or indirectly toone another. Such joining may be stationary in nature or moveable innature and such joining may allow for the flow of fluids, electricity,electrical signals, or other types of signals or communication betweenthe two members. Such joining may be achieved with the two members orthe two members and any additional intermediate members being integrallyformed as a single unitary body with one another or with the two membersor the two members and any additional intermediate members beingattached to one another. Such joining may be permanent in nature oralternatively may be removable or releasable in nature.

Referring to FIG. 1, a display 114 shows a variety of mobile phones 10,according to various exemplary embodiments. Mobile phones 10 come invarying shapes (e.g., style, external appearance, curvilinearity, etc.)and sizes (e.g., height, width, length, area, volume, etc.). Mobilephones 10 generally include a shell 12, a display 14, and a user inputdevice 16 (keypad, keyboard, button, trackball, touchscreen, end-userinput device, etc.). A shell 12 is a generally rigid structure orhousing configured to be grasped by a user and to protect the internalcomponents of the mobile phone 10 from liquids, debris, impact or othercontaminants. The shell 12 may include a removable cover configured toprovide access to internal components such as a battery, SIM card, etc.A touchscreen style of mobile phone, shown as mobile phone 10 a,includes a shell 12 a, a touch-sensitive display 14 a, one or more bezelor soft buttons 16 a. A classic (e.g., candybar) style of mobile phone,shown as mobile phone 10 b, includes a shell 12 b, a display 14 b, and akeypad 16 b. A clamshell (e.g., flip-phone) style of mobile phone, shownas mobile phone 10 c, includes a shell 12 c having an upper portion 17 cand a lower portion 18 c hingedly coupled by a joint 19. The clamshellmobile phone 10 c includes a display 14 c located on upper portion 17 c,and a keypad 16 c located on lower portion 18 c. A slideout (e.g.,slider) style of mobile phone, shown as mobile phone 10 d, includes ashell 12 d having an upper portion 17 d and a lower portion 18 d, whichare slidably coupled. The slideout mobile phone 10 d includes a display14 d, which may be touch-sensitive, located on upper portion 17 d, and akeypad 16 d (e.g., a numerical keypad, an alphanumeric keyboard, etc.)located on lower portion 18 d.

Referring to FIGS. 2A-2C, schematic block diagrams of a mobile phone 10,shown as the touchscreen style mobile phone, are shown, according toexemplary embodiments. The mobile phone 10 is shown to include a shell12, an antenna 20, and a processing electronics 104. The antenna 20 maybe configured for communication with a cellular network, and the antenna20 and the processing electronics 104 may be coupled to the shell 12,either directly or indirectly (e.g., via a circuit board, etc.).According to an exemplary embodiment, some hardware components arenon-interchangeable. For example, the display 14, keyboard 18,processing electronics 104 (e.g., processor, etc.), antenna 20, and acamera may be may be permanently fixed to the shell or coupled to theshell 12 in a manner that is not intended for interchangeability or in amanner that makes interchanging hardware components prohibitivelydifficult. For example, the display 14 may be coupled to the shell 12with the use of an adhesive (e.g., a room temperature vulcanizationadhesive).

Briefly referring to FIG. 9, a detailed block diagram of the processingelectronics 104 of FIG. 2A is shown, according to an exemplaryembodiment. Processing electronics 104 includes a memory 120 andprocessor 122. Processor 122 may be or include one or moremicroprocessors, an application specific integrated circuit (ASIC), acircuit containing one or more processing components, a group ofdistributed processing components, circuitry for supporting amicroprocessor, or other hardware configured for processing. Accordingto an exemplary embodiment, processor 122 is configured to executecomputer code stored in memory 120 to complete and facilitate theactivities described herein. Memory 120 can be any volatile ornon-volatile memory device capable of storing data or computer coderelating to the activities described herein. For example, memory 120 isshown to include modules 128-130 which are computer code modules (e.g.,executable code, object code, source code, script code, machine code,etc.) configured for execution by processor 122. When executed byprocessor 122, processing electronics 104 is configured to complete theactivities described herein. Processing electronics includes hardwarecircuitry for supporting the execution of the computer code of modules128-130. For example, processing electronics 104 includes hardwareinterfaces (e.g., output 150) for communicating control signals (e.g.,analog, digital) from processing electronics 104 to one or more circuitscoupled to processing electronics 104. Processing electronics 104 mayalso include an input 155 for receiving data or signals from othersystems or devices.

Memory 120 is shown to include a memory buffer for receiving and storingdata, for example user input, downloaded data, etc., until it isaccessed by another module or process. Memory 120 is further shown toinclude a communication module 128, which may include logic forcommunicating between systems and devices. For example, thecommunication module 128 may be configured to use an antenna or dataport for communication over a network. The communication module 128 mayfurther be configured to communicate with other components within themobile phone over a parallel bus, serial bus, or network. Memory 120 isfurther shown to include a user interface module 130, which includeslogic for using user input data in memory buffer 124 or signals frominput 155 to determine desired user responses. For example, the userinterface module 130 may be configured to convert, transform, or processsignals or data from a keyboard, mouse, or touchscreen into signals ordata useable by processor 122.

The shell 12 is further shown to include one or more receivers 22 (e.g.,portion, region, socket, connector, etc.), shown as, a first receiver 22a and a second receiver 22 b, which may be coupled directly orindirectly (e.g., via a circuit board, etc.) to the shell 12. Eachreceiver 22 is configured to receive, support, or couple to a hardwarecomponent 24 (e.g., interchangeable hardware component, selectablehardware component, widget, element, etc.) of a certain size andconfiguration. As shown, the first receiver 22 a is configured toreceive a first hardware component 24 a selected from a first set ofcomponents having substantially the same size but different functions.Hardware components 24 selected from the first set of hardwarecomponents may be interchangeable (e.g., swappable, substitutable, etc.)with other hardware components 24 in the first set of components.According to one embodiment, the interchangeable hardware components 24of the first set have substantially the same shape.

The mobile phone 10 may include a second receiver 22 b, which isconfigured to receive a second hardware component 24 b selected from asecond set of components having substantially the same size butdifferent functions. The first receiver 22 a and the second receiver 22b may be the same or different sizes. According to an exemplaryembodiment, the first receiver 22 a and the second receiver 22 b havesimilar dimensions (e.g., length, width, area, volume, etc.), in whichcase a hardware component 24 may be installed in either the firstreceiver 22 a or the second receiver 22 b. It is not necessary thatevery receiver 22 have a hardware component 24 directly coupled (e.g.,plugged in, inserted, installed, snapped in, connected, etc.) to it. Forexample, referring to FIG. 2A, a first hardware component 24 a iscoupled to the first receiver 22 a, but no hardware component is coupledto the second receiver 22 b.

Referring to FIG. 2C, it is further contemplated that a larger hardwarecomponent, shown as third hardware component 24 c, may be disposed inboth the first receiver 22 a and the second receiver 22 b. The thirdhardware component may be selected from a third set of components havingsubstantially the same size but different function.

Each receiver 22 may include one or more electrical contacts 26 whichare configured to electrically couple to the hardware component 24.According to an exemplary embodiment, each of a set of hardwarecomponents 24 is configured to electrically couple to a set ofelectrical contacts 26. Referring to FIGS. 2A-2B, a hardware component24 may be configured to couple only to the contacts 26 in one receiver22. Referring to FIG. 2C, a hardware component 24 may be configured tocouple to contacts 26 in more than one receiver 22.

Referring generally to FIGS. 2-4, the hardware component 24 may havecompatible shapes and sizes. For example, a set of hardware components24 may be the same size and, therefore, be exchangeable betweenreceivers 22. A set of hardware components 24 may be mutuallyinterchangeable. For example, a third hardware component 24 c may be thesame size as the combination of a first hardware component 24 a and asecond hardware component 24 b. As described above, a set of hardwarecomponents 24 may be include pre-specified electrical connections 28 tothe mobile phone 10. As shown, in FIG. 2B, the number and arrangement ofthe contacts 26 in first receiver 22 a and second receiver 22 b enablesthe first and second hardware component 24 a, 24 b to be placed ineither receiver. As shown, in FIG. 2C, the number and arrangement ofcontracts 26 in the first and second receivers 22 a, 22 b enables thethird hardware component 24 c to be installed across both receivers 22.Providing a standardized number and arrangement of contacts in thereceivers 22 facilitates construction of hardware components that arecompatible with the mobile phone 10. It is further contemplated that aset of hardware components may include pre-specified optical connectionsto the mobile phone 10, and that the hardware components 24 may includepre-specified electrical or optical connections to each other. Forexample, the third hardware component 24 c may be configured to allowthe first hardware component 24 a to piggy-back thereon. Enablingpiggy-backing facilitates the installation of larger or multi-receiverhardware components 24 without inherently requiring the removal of otherhardware components. A set of hardware components 24 may have standardsizes or power consumptions to facilitate interchangeability. A set ofhardware components may be configured to have a standard componentdimensions (e.g., area, volume, etc.) or to fit within a standard shellvolume.

The hardware components 24 may have a variety of functions. According toone embodiment, a hardware component 24 may be a connector, e.g., aUniversal Serial Bus (USB) connector, an IEEE 1394 connector, aDisplayPort connector, a Digital Visual Interface connector, a coaxialcable connector, a High Definition Multimedia Interface connector, aregistered jack, a TRS connector, or miniaturized versions thereof. Inthis embodiment, a user may insert a TRS connector hardware componentinto a first receiver 22 a in order to output an analog signal, forexample, to headphones. The user may then replace the TRS connectorhardware components with a mini-USB connector hardware component inorder to output a digital signal, for example, to a computer. Accordingto an exemplary embodiment, the processing electronics 104 may includecomputer code (e.g., software, firmware, drivers, etc.) in theconfiguration data 126 of memory 120 to support communication betweenthe processing electronics 104 and the hardware component. According toanother embodiment, the hardware component 24 may include computer code(e.g., software, firmware, drivers, etc.) configured to supportcommunication between the hardware component 24 and the processingelectronics 104.

According to various other embodiments, the hardware component 24 mayinclude an ultrasonographic transducer, a heart monitor, a blood glucosetester, or an infrared camera. The hardware component 24 may include amicro impulse radar transducer, which may be configured to detect aheartbeat or the presence of an object or person on the other side of awall or door. The hardware component 24 may include a food tester, forexample, componentry configured to detect the presence of an allergensuch as peanuts, fish, dairy, etc. The hardware component 24 may includea magnetic stripe reader, which may be used for the swiping or readingof data stored on a credit card. The hardware component 24 may includean RFID reader, which may be used for detecting and receivinginformation on a radio-frequency identification chip. The hardwarecomponent 24 may include an accident data recorder (e.g., flightrecorder, black box, etc.), which may be configured for example torecord location, velocity, acceleration information. The accident datarecorder may include an accelerometer or gyroscope and may be configuredto store peak information data or to stop overwriting data in responseto a severe acceleration or deceleration. This may be useful, forexample, for accident reconstruction purposes or for a parent monitoringthe driving behavior of a teenage dependent. The hardware component 24may include a power source (e.g., fuel cell, battery, solar cell, etc.).According to one embodiment, a small battery may couple a first receiver22 a, and larger battery (e.g., more powerful, longer life, etc.) maycouple to first and second receivers 22 a, 22 b. The hardware componentmay include processing electronics (e.g., a microprocessor, memoryetc.). For example, a user may insert a graphics processing unit intothe mobile phone 10 to improve a gaming experience, or to support avideo projector (which may be another hardware component 24). Thehardware component 24 may include a display. For example, a user mayinstall a hardware component 24 containing additional volatile memory(e.g., RAM) or non-volatile memory (e.g., flash memory, etc.). Accordingto another embodiment, the user may install a card reader hardwarecomponent (e.g., SIM card, SD card, etc.) into the mobile phone 10. Thehardware component 24 may include a speaker or a microphone tofacilitate the playing or recording of audio signals. The hardwarecomponent 24 may include a keyboard, keypad, trackball, touchpad, orother user input device. The hardware component 24 may include abiometric identification reader (e.g., fingerprint reader, retinalscanner, etc.), which may be used to enhance security of the mobilephone 10. The hardware component 24 may include an antenna (e.g.,shortwave radio, amplitude modulation (AM), frequency modulation (FM),global system for mobile communication (GSM), code division multipleaccess (CDMA), 3G, 4G, global positioning system (GPS), echolocation(e.g., sonar), etc.), which may allow a user to receive or transmitsignals. For example, a user having a 3G antenna, may elect to replacethe antenna with a 4G antenna when the technology becomes available intheir location, or a user may elect to replace a CDMA antenna with a GSMantenna when travelling in a GSM dominant country. For another example,a user may install an AM or FM antenna in order to listen to a radiobroadcast.

According to a preferred embodiment, the hardware component 24 isdisposed at least partially within the shell 10. For example, it iscontemplated that a transducer, connector, or camera may extendpartially out of the shell 10 in order to emit, connect, or receive asnecessary. According to other embodiments, the hardware component 24 isdisposed completely within the shell 10. In these embodiments, it may benecessary to open the shell 10 (e.g., remove a cover) in order to removeor swap a hardware component 24.

According to various embodiments, the first hardware component 24 a, thesecond hardware component 24 b, the third hardware component 24 c, orthe interchangeable hardware components 24 generally may be selected byand end-user. An end-user may be a purchaser of the mobile phone 10 oran intended long-term possessor. According to other embodiments, theend-user may be an intermediary, for example, a person configuring thephone to resell (e.g., a retailer), lease, gift, (e.g., friend, family,etc.), or provide (e.g., coworker, employer, IT department, etc.) toanother.

Referring to FIG. 3, a schematic block diagram of a mobile phone 10,shown as a clamshell style mobile phone 10 c, is shown according to anexemplary embodiment. As shown, the size and shape of the mobile phone10 may dictate that only one receiver 22 can fit within the shell 12.Accordingly, the mobile phone 10 of FIG. 3 would not be able to acceptthe hardware component 24 c of FIG. 2C. Thus, a hardware component 24for use in the mobile phone 10 may be selected from a subset ofcomponents that are compatible with the size and shape of the receiverof the mobile phone 10.

Referring to FIGS. 4A-4D, cross-sectional schematic block diagrams of amobile phone 10, shown generally as the a touchscreen style of mobilephone 10 a of FIG. 1, are shown according to exemplary embodiments. Themobile phone 10 of FIG. 4A is shown to include a shell 12 having arelatively thin cross-section and to include a first receiver 22 a. Incontrast, the mobile phones 10 of FIGS. 4B-4D are shown to includeshells 12 having thicker cross-sections, which accommodate a secondreceiver 22 b and a third receiver 22 c below or behind the firsthardware component 24 a, the processing electronics 104, and the antenna20. The mobile phone 10 of FIG. 4B is shown to accommodate a longerhardware component 24 d across (e.g., in, among, between, etc.) thesecond receiver 22 b and third receiver 22 c. The mobile phone 10 ofFIG. 4C is shown to accommodate a thicker hardware component 24 e across(e.g., in, among, between, etc.) the first receiver 22 a and the secondreceiver 22 b. As shown, the third receiver 22 c is configured toreceive a different sized hardware component 24 than each of first andsecond receivers 22 a, 22 b. Accordingly the set of hardware components24 configured to fit into the third receiver 22 c are interchangeablewith each other, but are not interchangeable with the set of hardwarecomponents 24 configured to fit into the first or second receivers 22 a,22 b. The mobile phone 10 of FIG. 4D is shown to accommodate a larger,more complex hardware component 24 f across (e.g., in, among, between,etc.) the first receiver 22 a, the second receiver 22 b, and the thirdreceiver 22 c. According to the embodiments shown, the thicker hardwarecomponents 24 e, 24 f of FIGS. 4C and 4D would not fit into the thinshell of FIG. 4A. According to various other embodiments, the number andarrangement of receivers 22 and the shape and size of hardwarecomponents 24 create a vast number of possible combinations of hardwarecomponents 24 within a shell 12, and, in effect, create athree-dimensional puzzle.

In contrast, conventional wisdom has been to constantly drive mobilephones to be smaller and smaller, thinner and thinner. Theseever-shrinking phones leave no room for extra components, let aloneinterchangeable hardware components. However, with the customizablemobile phones disclosed herein, a user may select a larger (e.g., wider,longer, thicker, etc.) mobile phone in order to accommodate additionalreceivers or to accommodate a particularly desired selectable hardwarecomponent. Alternatively, a user may select a smaller phone knowing thathe or she may swap out the interchangeable hardware components.

It should be noted that a particular style of mobile phone 10 does notinherently dictate its size or the number of receivers 22 within itsshell 12. For example, the clamshell style mobile phone 10 c of FIG. 3is shown to only include one receiver 22; however, a user may select alonger, wider, or thicker clamshell phone 10 c in order to accommodateadditional receivers 22 or additional or larger selectable hardwarecomponents 24.

According to one embodiment, the portion of the volume of theinterchangeable hardware components 24 occupy a greater portion of thevolume of the shell 12 than the non-interchangeable hardware components(e.g., display 14, user input device 16, processing electronics 104, andantenna 20. According to another embodiment, the interchangeablehardware components 24 occupy at least 50 percent of the volume of theshell 12. According to another embodiment, the interchangeable hardwarecomponents 24 occupy at least 90 percent of the volume of the shell 12.

Referring to FIGS. 1 and 5-8, a system in which a user (e.g., anend-user) may customize a mobile phone is shown according to anexemplary embodiment. A client 110 is shown to communicate with a server102 over a network 100 (e.g., local area network, wide area network,internet, etc.). The client 110 may include display 114, processingelectronics 104 c, and a user input device 116. The user input device116 may be a keyboard, a keypad, a mouse, a trackball, a touchscreen,etc. The client 110 may be any suitable computing device, for example, ahome computer, a portable computing device, a mobile phone, an in-storekiosk, etc.

As described above with respect to processing electronics 104, andreferring generally to FIG. 9, processing electronics 104 c may includea memory 120 and processor 122. Processor 122 may be or include one ormore microprocessors, an application specific integrated circuit (ASIC),a circuit containing one or more processing components, a group ofdistributed processing components, circuitry for supporting amicroprocessor, or other hardware configured for processing. Accordingto an exemplary embodiment, processor 122 is configured to executecomputer code stored in memory 120 to complete and facilitate theactivities described herein. Memory 120 can be any volatile ornon-volatile memory device capable of storing data or computer coderelating to the activities described herein. For example, memory 120 isshown to include modules 128-132 which are computer code modules (e.g.,executable code, object code, source code, script code, machine code,etc.) configured for execution by processor 122. When executed byprocessor 122, processing electronics 104 c are configured to completethe activities described herein. Processing electronics include hardwarecircuitry for supporting the execution of the computer code of modules128-132. For example, processing electronics 104 c include hardwareinterfaces (e.g., output 150) for communicating control signals (e.g.,analog, digital) from processing electronics 104 c to one or morecircuits coupled to processing electronics 104 c. Processing electronics104 c may also include an input 155 for receiving data or signals fromother systems or devices. Memory 120 is shown to include a customizationmodule 132 which may include logic for transforming data or signals froma user input module 130 or memory buffer 124 into information (e.g.,selection information, preference information, etc.) which may be sentto the server 102.

The server 102 is shown to include processing electronics 104 s. Asdescribed above with respect to processing electronics 104 and 104 c,and referring generally to FIG. 9, the processing electronics 104 s mayinclude a memory 120 and processor 122. Processor 122 may be or includeone or more microprocessors, an application specific integrated circuit(ASIC), a circuit containing one or more processing components, a groupof distributed processing components, circuitry for supporting amicroprocessor, or other hardware configured for processing. Accordingto an exemplary embodiment, processor 122 is configured to executecomputer code stored in memory 120 to complete and facilitate theactivities described herein. Memory 120 can be any volatile ornon-volatile memory device capable of storing data or computer coderelating to the activities described herein. For example, memory 120 isshown to include modules 128 and 134 which are computer code modules(e.g., executable code, object code, source code, script code, machinecode, etc.) configured for execution by processor 122. When executed byprocessor 122, processing electronics 104 s are configured to completethe activities described herein. Processing electronics include hardwarecircuitry for supporting the execution of the computer code of modules128 and 134. For example, processing electronics 104 s includes hardwareinterfaces (e.g., output 150) for communicating control signals (e.g.,analog, digital) from processing electronics 104 s to one or morecircuits coupled to processing electronics 104 s. Processing electronics104 s may also include an input 155 for receiving data or signals fromother systems or devices. Memory 120 is shown to include a compatibilitymodule 134 which may include logic for receiving selection or preferenceinformation from a client and providing a set of compatible shells or aset of compatible hardware components.

The user may first select a mobile phone shell 12 from a set of mobilephone shells 12. Referring to FIG. 5, the user may select from a list 51of shells, for example, shown on a display 114. The user may select fromthe list 51 by selecting or clicking on the text, checking a box,selecting a radio button, or any other suitable method of selection.Referring to FIG. 1, the user may select from one or more images 53, 55of the mobile phone shells 12, for example, shown on a display 114. Thelist or images of the mobile phone shells 12 may be provided by andcaused to be displayed by the server 102. The set of shells 12 mayinclude different styles, shapes, and sizes of mobile phone shells. Theuser may select a mobile phone shell 12 based on at least one of size,volume, and shape. The user may also provide or select a weightpreference information (e.g., preferred weight of the mobile phone, apreferred weight range of the mobile phone, a priority of the weight ofthe mobile phone relative to other factors, etc.). The user may alsoprovide or select a cost preference information (e.g., preferred cost orprice of the mobile phone, a preferred cost or price range of the mobilephone, a priority of the cost or price the mobile phone relative toother factors, etc.).

The user selection may be sent from the client 110 to the server 102 asshell selection information. If provided, the weight preferenceinformation and the cost preference information may also be sent fromthe client 110 to the server 102. The server 102, in turn, receives theshell selection information, weight preference information, and/or thecost preference information. The server 102 may generate or identify asubset of all available hardware components based on a compatibilitybetween hardware components 24 and the shell corresponding to the shellselection information. According to another embodiment, the server 102may receive the generated set of hardware components 24 from anothercomputer.

The compatibility between the mobile phone shell 12 and the selectableor interchangeable hardware components 24 may be based on at least onesize value (e.g., length, width, thickness, area, volume, shape, etc.).For example, the volume of the thicker hardware component 24 e of FIG.4C would not fit within the thinner shell 12 of FIG. 4A. Similarly, thecomplex hardware component 24 f of FIG. 4D would not fit within theshells 12 of FIG. 3 or 4A. The compatibility may be based on at leastone of the number and arrangement of receivers 22 and electricalcontacts 26 available in the shell 12 that corresponds to the shellselection information. If received, compatibility may be based on theweight preference information and/or the cost preference information.

The server 102 may then provide a subset of hardware components 24 thatare compatible with the selected mobile phone shell 12. Referring toFIGS. 6 and 7, the subset of compatible hardware components 24 may beprovided as a list 61 or as an image 70. The server may also provide anauxiliary information relating to the hardware components 24. Forexample, the list 61 or image 70 may also include a size, a weight, acost, a rating, and a backlog (i.e., time until delivery) of thehardware component. The subset of selectable hardware components 24which are incompatible with the shell selection information (e.g., arenot part of the subset of compatible hardware components 24 generatedbased on a compatibility between hardware components 24 and the selectedshell 24) may either not be provided or may be provided along with anindicia of incompatibility (e.g., strikethrough, grayed out, dashedoutline, etc.). According to another embodiment, the subset of hardwarecomponents 24 may be stored to a memory for use in a non-graphicalprocess, e.g., an order fulfillment system. For example, the output maybe provided to an assembly facility as described further below.

The system may also provide an indication that the compatibility of ahardware component 24 with the shell selection information is dependentupon one or more criteria. For example, the server 102 may provide anindication that a second hardware component 24 b may not also fit in theselected mobile phone shell due to the size of a first hardwarecomponent 24 a. Referring briefly to FIG. 7, the server 102 may providean indication 78 that a power hungry hardware component (e.g., heartmonitor hardware component 76) requires a larger battery (e.g., XLbattery hardware component 74). The server 102 may provide an indicationthat two power hungry hardware components should not both be installedinto the same mobile phone. The server 102 may provide an indication 79that a hardware component 24 is incompatible with the selected shell 12or may be compatible with a different shell 12. For example, the server102 may suggest that a popular hardware component 24 is compatible witha mobile phone shell 12 that is thicker or longer than the presentlyselected shell.

The provided subset of hardware components 24 may include individualhardware components 24 or combinations of hardware components compatiblewith the shell selection information. One combination may includerelated items, for example, a mini-USB connector, a mini-DisplayPortconnector, and a mini-HDMI connector. Another combination may include apower hungry hardware component and a larger battery. Anothercombination may be profession specific; for example, a heart monitorhardware component and an ultrasonographic transducer hardwarecomponent. Another combination may include specifically packagedhardware components; for example, a larger battery being longer ratherthan thicker in order to fit in the selected shell with another hardwarecomponent. Yet another combination may include a speaker hardwarecomponent and a microphone hardware component.

The user may further customize the mobile phone 10 by selecting at leastone compatible hardware component 24 from the set or subset of hardwarecomponents that are compatible with the selected shell 12. Referring toFIG. 7, a user may select the desired hardware component 24 by placing(e.g., moving, dragging, etc.) an image 80 of a hardware component 24 inan image 70 of the selected mobile phone shell 12. For example, the usermay drag the “RAM” hardware component 71 from its location on the rightside of the display 114 to one of the available receiver 22 a-dlocations. The user may reconfigure the interchangeable hardwarecomponents 24 as desired. For example, a right-handed user may put amini-USB connector hardware component 73 on the right side of the shell12 in order to facilitate connection and disconnection of a USB cable ordevice. The user selection may be sent from the client 110 to the server102 as a first hardware selection information, and the server 102, inturn, may receive the first hardware selection information.

According to various other embodiments, the system may receive othertypes of information, for example, prior use information, ratinginformation, manufacturing information, etc. Prior use information mayinclude how often the battery was charged, the depth of the mean ormedian battery cycle, number of calls received, number of calls dropped,number of text messages sent, acceleration data, etc. The prior useinformation may be provided by a user, retrieved from the user's accountinformation, or retrieved from the user's current phone. For example,the prior use information may be retrieved from a prior use recorderhardware component in the user's current mobile phone. The battery usageinformation may be used by the system to suggest an appropriately sizedbattery. The number of texts sent may be used to suggest a particularstyle of phone (e.g., a phone with a full keyboard) or texting plan. Theacceleration (e.g., number of times the phone was dropped) may be usedto suggest a more rugged shell, more rugged hardware components, aprotective covering for the shell, or increased phone insurance. Ratinginformation 63 may include ratings based on popularity, based on otherusers' opinions, or based on objective functionality testing. Themanufacturing information may include manufacturing complexity (e.g.,fitting two large hardware components tightly in a small shell) oravailability of a hardware component (e.g., a backorder, or rarelypurchased). The set of hardware components that are compatible with theselected shell and hardware may be updated in response to additionalinformations received.

The server 102 may then provide a set of second hardware components 24,the set of second hardware component generated based on a compatibilitybetween the second hardware component, the first hardware selectioninformation, and shell selection information. For example, if a userselects a small, lightweight battery as a first hardware component 24,the updated set of hardware components may not include power hungryhardware components. Similarly, if the first selected hardware componentis a large component, other large components may be removed from theupdated sets. The system may continue to update the sets of compatiblehardware as the user selects and deselects hardware components and shellstyles, shapes, and size.

According to one embodiment, a user may select a preconfigured mobilephone 10. The preconfigured mobile phone 10 includes one or morehardware components 24 already in place in a receiver 22 and may includeone or more empty receivers 22. The set of preconfigured phones 10 maybe provided to the user based on price, popularity, a desire to reduceinventory of particular components, cost, etc. According to oneembodiment, a mobile phone 10 may be preconfigured by a designer to havea certain shell 12 (e.g., colors, logos, pattern, print, picture,texture, etc.) and hardware components 24. According to anotherembodiment, the phone 10 may be preconfigured with combinations ofhardware components 24, as described above. A user may then select froma subset of interchangeable hardware components 24 which are compatiblewith the one or more empty receivers 22.

According to another embodiment, the user may first select one or morehardware components 24. The user may select from a list 61 of hardwarecomponents 24 or from one or more images 80 of hardware components 24.The user may select the hardware components 24 individually or select apredefined combination of hardware components 24. The user is thenprovided with a set of mobile phone shells 12 generated based on acompatibility between the mobile phone shells 12 and the selectedhardware components 24. The set of mobile phone shells 12 may beprovided as a list 51 or as one or more images 53, 55. The compatibilitymay be based on at least one size value (e.g., length, area, thickness,volume, etc.), the number or orientation of receivers 22 or electricalcontacts 26 within the shell, etc. The user may also provide or selectcost preference information, weight preference information, or shellpreference information (e.g., a shell style, shell shape, shell size,shell color, etc.). These preferences may be factored into determiningthe set of mobile phone shells 12 to be provided to the user.

The set of mobile phone shells 12 provided may be standard or customshells. For example, after selecting certain “must have” hardwarecomponents 24 which do not fit in one of the available shells 12, theuser may be given the option of having a custom shell 12 made to fit thecomponents.

As described above, the system may provide an indication of dependencybetween certain hardware components 24 and between certain hardwarecomponents 24 and shells 12. The server 102 may also provide anindication that a particular hardware component 24 is causing anincompatibility with a shell 12. For example, if the user picked onethick hardware component 24, the system may provide an indication thatthat thick hardware component is preventing the selection of a thinmobile phone shell 12. The server 102 may further provide a suggestionof alternative components which may have the same functionality, butsolve the incompatibility. Further, suggestions may be based onoptimizations of space, weight, cost, etc. Besides using an optimizationapproach, heuristic, rule-based, or other ad-hoc approaches may be usedto generate suggestions. For example, a user may have selected aninexpensive but larger hardware component 24, and the system may suggestthe more expensive but smaller hardware component. The smaller hardwarecomponent 24 may then be compatible with thinner or otherwise smallermobile phone shells 12.

The system may be configured to update the sets or subsets of selectablehardware components 24 and shells 12 in substantially real time. Forexample, upon selecting a first hardware component 24, the system mayremove or indicate incompatibility of a subset of mobile phone shells12. Or upon deselecting a hardware component 24, the system can causeother hardware components 24 and mobile phone shells 12 to be shown ascompatible. According to one embodiment, selection of a hardwarecomponent 24 having a large volume may remove a mobile phone shell 12having a small volume from possible selection. Thus a user may see howeach hardware component 24 affects his or her options for mobile phoneshells 12. After selecting a shell 12, the set of compatible hardwarecomponents 24 may be updated. For example, the system may provide asubset of hardware components 24 which are compatible with thepreviously selected hardware components 24 and the selected mobile phoneshell 12. The user may continue to select additional hardware components24 to fill out the remaining receivers 22 a-d. Compatibility subsets,indications of dependency, and suggestions, may be updated with eachadditional selection.

According to another embodiment, the client 110 of FIG. 8 may downloadmobile phone shell set data, hardware component set data, compatibilitydata, dependency data, and other necessary information for mobile phonecustomization from one or more servers 102. For example, thecompatibility module 134 on the server 102 may be configured to providephone shell set data, hardware component set data, compatibility data,and dependency data to a client 110. The customization module 132 on theclient 110 may then receive information (e.g., selection information,preference information, etc.) from the user input device 116 or userinterface module 130. The customization module 132 may then generatesets of shells 12 and hardware components 24 based on compatibility andprovide the sets to processor 122, display 114, output 150, or anothermodule. For example, the user may select a mobile phone shell 12 from aset of mobile phone shells 12, and the customization module 132generates a subset of interchangeable hardware components 24 havingdifferent functions, the subset of interchangeable hardware components24 being generated based on the compatibility between the selectedmobile phone shell 12 and the set of available interchangeable hardwarecomponents 24.

Using the systems and methods described herein, one may offer to sell ahardware customizable mobile phone 110 with selectable hardwarecomponents 24 to fit within a shell 12. The seller may offer one or moremobile phone shells 12, and the seller may receive a selection of amobile phone shell. The seller may offer a one or more selectableoptions for at least one hardware component 24 configured to fit withinthe mobile phone shell 12, and the seller may receive a selection of atleast one hardware component configured to fit within the shell.

According to one embodiment, a seller may provide a price discount on amobile phone 10 in exchange for the buyer purchasing a mobile phone 10with a certain hardware component 24. According to another embodiment, alessor may provide a discounted mobile phone 10 to a lessee if themobile phone 10 contains an accident data recorder hardware component ora prior use information recorder hardware component. The accident datarecorder or prior use information recorder hardware components may havea particular configuration (e.g., shape, electrical contacts, encryptionkey, lock, etc.) which corresponds to a particular receiver 22 in themobile phone 10; thus making removing or replacing the recorder hardwarecomponent prohibitively difficult.

Further using the systems and methods described herein, an aftermarketcustomizer may sell interchangeable hardware components 24. For example,if a user already has a customizable mobile phone 10, the user may use asystem to determine if another interchangeable hardware component 24will fit in their mobile phone 10. It is contemplated that some originalequipment manufacturers will use hardware or software locks on theinterchangeable hardware components 24 or the receivers 22 in the mobilephone shells 12 in order to inhibit the use of uncertified orcounterfeit hardware components 24.

The selected shell and hardware components may be provided to anassembler (e.g., assembly facility, manufacturer, manufacturingfacility, etc.). The assembler may receive one or more styles, shapes,or sizes of mobile phone shells 12. The assembler may also receive aplurality of interchangeable hardware components 24 which are configuredto fit with the mobile phone shells 12. Then the assembler may assembleone or more interchangeable hardware components 24 into a mobile phoneshell 12 in response to an order. The hardware customizable mobile phone10 may be assembled in response to a specific customization (e.g., by anend-user) or in response to a general order. For example, a retailer mayorder several of a particular configuration due to its popularity.Another retailer may order a particular configuration because a certaincelebrity has that configuration.

Referring to FIG. 10, a flowchart of a process 200 for customizinghardware for a mobile phone is shown, according to an exemplaryembodiment. Process 200 is shown to include the steps of receiving shellselection information from a user input device (step 202), identifying aset of hardware components, the set of hardware components generatedbased on a compatibility between the hardware components and the shellselection information (step 204), and outputting the set of identifiedcompatible hardware components (step 206). For example, accordingvarious embodiments, the step 202 of receiving the shell selectioninformation includes receiving from a memory, a communication interface,or user input device; the step 204 of identifying the set of hardwarecomponents may be performed at processing electronics; and the step 206of outputting the set of components includes outputting to a memory,display interface, or communication interface.

Referring to FIG. 11, a flowchart of a process 210 for customizinghardware for a mobile phone is shown, according to an exemplaryembodiment. Process 210 is shown to include the steps of providing a setof mobile phone shells (step 212), receiving shell selection information(step 214), identifying a set of hardware components, the set ofhardware components generated based on a compatibility between thehardware components and the shell selection information (step 220), andoutputting the set of identified compatible hardware components (step222). Process 210 may also include one or more of the steps of receivingweight preference information (step 216) and receiving cost preferenceinformation (step 218).

Referring to FIG. 12, a flowchart of a process 230 for customizinghardware for a mobile phone is shown, according to an exemplaryembodiment. Process 230 is shown to include the steps of receiving shellselection information (step 232), identifying a set of hardwarecomponents, the set of hardware components generated based on acompatibility between the hardware components and the shell selectioninformation (step 234), outputting the set of identified compatiblehardware components (step 236), receiving first hardware selectioninformation (step 238), identifying a set of compatible second hardwarecomponents, the set of second hardware components generated based on acompatibility between the second hardware components, the first hardwareselection information, and the shell selection information (step 240),and outputting the set of identified second compatible hardwarecomponents (step 242). Process 230 may further include the step ofproviding an indication that the compatibility of a hardware componentwith the shell selection information is dependent upon one or morecriteria (step 244).

Referring to FIG. 13, a flowchart of a process 300 for customizinghardware for a mobile phone is shown, according to an exemplaryembodiment. Process 300 is shown to include the steps of receivinghardware component selection information (step 302), identifying a setof compatible mobile phone shells, the set of mobile phone shellsgenerated based on a compatibility between the mobile phone shells andthe hardware component selection information (step 304), and outputtingthe identified set of compatible mobile phone shells (step 306). Forexample, according various embodiments, the step 302 of receiving thehardware component selection information includes receiving from amemory, a communication interface, or user input device; the step 304 ofidentifying the set of mobile phone shells may be performed byprocessing electronics; and the step 306 of outputting the set of mobilephone shells includes outputting to a memory, display interface, orcommunication interface.

Referring to FIG. 14, a flowchart of a process 310 for customizinghardware for a mobile phone is shown, according to an exemplaryembodiment. Process 310 is shown to include the steps of providing a setof hardware components (step 312), receiving hardware componentselection information (step 314), identifying a set of compatible mobilephone shells, the set of mobile phone shells generated based on acompatibility between the mobile phone shells and the hardware componentselection information (step 320), and outputting the identified set ofcompatible mobile phone shells (step 322). Process 310 may also includeone or more of the steps of receiving weight preference information(step 316) and receiving cost preference information (step 318).

Referring to FIG. 15, a flowchart of a process 330 for customizinghardware for a mobile phone is shown, according to an exemplaryembodiment. Process 330 is shown to include the steps of receivinghardware component selection information (step 332), identifying a setof mobile phone shells, the set of mobile phone shells generated basedon a compatibility between the mobile phone shells and the hardwarecomponent selection information (step 334), outputting the identifiedset of compatible mobile phone shells (step 336), receiving shellselection information (step 338), identifying a set of second compatiblehardware components, the set of second hardware components generatedbased on a compatibility between the second hardware components, thehardware component selection information, and the shell selectioninformation (step 340), and outputting the set of second compatiblehardware components (step 342). Process 330 may further include the stepof providing an indication that the compatibility of a mobile phoneshell with the hardware component selection information is dependentupon one or more criteria (step 340).

Referring to FIG. 16, a flowchart of a process 350 for customizinghardware for a mobile phone is shown, according to an exemplaryembodiment. Process 350 is shown to include the steps of receivinghardware component selection information (step 352), receiving shellpreference information (step 354), identifying a set of mobile phoneshells, the set of mobile phone shells generated based on acompatibility between the mobile phone shells, the hardware componentselection information, and the shell preference information (step 356),and outputting the identified set of mobile phone shells (step 358).According to various embodiments, the shell preference information mayinclude a shell shape, shell style, and shell size.

Referring to FIG. 17, a flowchart of a process 400 for customizinghardware for a mobile phone is shown, according to an exemplaryembodiment. Process 400 is shown to include the steps of selecting amobile phone shell from a set of mobile phone shells (step 402) andselecting at least one hardware component from a subset ofinterchangeable hardware components having different functions, thesubset of interchangeable hardware components generated based on acompatibility between the selected mobile phone shell and the set ofavailable interchangeable hardware components (step 404).

Referring to FIG. 18, a flowchart of a process 410 for customizinghardware for a mobile phone is shown, according to an exemplaryembodiment. Process 410 is shown to include the steps of selecting amobile phone shell from a set of mobile phone shells (step 412) andselecting at least one hardware component from a subset ofinterchangeable hardware components having different functions, thesubset of interchangeable hardware components generated based on acompatibility between the selected mobile phone shell and the set ofavailable interchangeable hardware components (step 418). Process 410may also include one or more of the steps of providing weight preferenceinformation (step 414) and providing cost preference information (step416).

Referring to FIG. 19, a flowchart of a process 420 for customizinghardware for a mobile phone is shown, according to an exemplaryembodiment. Process 420 is shown to include the steps of selecting apreconfigured mobile phone from a set of mobile phone shells, thepreconfigured mobile phone including at least one empty portionconfigured to receive an interchangeable hardware component (step 422)and selecting at least one hardware component from a subset ofinterchangeable hardware components having different functions, thesubset of interchangeable hardware components generated based on acompatibility between the selected mobile phone shell and the set ofavailable interchangeable hardware components (step 424).

Referring to FIG. 20, a flowchart of a process 430 for customizinghardware for a mobile phone is shown, according to an exemplaryembodiment. Process 430 is shown to include the steps of selecting amobile phone shell from a set of mobile phone shells (step 432), causingan image of at least one hardware component from a subset ofinterchangeable hardware components to move form a first location to asecond location, the second location corresponding to a portion withinthe selected mobile phone shell and the subset of interchangeablehardware components generated based on a compatibility between theselected mobile phone shell and the set of available interchangeablehardware components (step 434), and selecting at least one hardwarecomponent from a subset of interchangeable hardware components havingdifferent functions (step 436).

Referring to FIG. 21, a flowchart of a process 500 for selling a mobilephone is shown, according to an exemplary embodiment. Process 500 isshown to include the steps of offering to sell a hardware customizablemobile phone with one or more selectable hardware components configuredto fit within a shell (step 502), offering a plurality of selectableoptions for at least one hardware component configured to fit within theshell (step 504), and receiving a selection of at least one hardwarecomponent configured to fit within the shell (step 506).

Referring to FIG. 22, a flowchart of a process 510 for selling a mobilephone is shown, according to an exemplary embodiment. Process 510 isshown to include the steps of offering to sell a hardware customizablemobile phone with one or more selectable hardware components configuredto fit within a shell (step 512), receiving prior user information (step514), offering a plurality of selectable options for at least onehardware component configured to fit within the shell (step 516), andreceiving a selection of at least one hardware component configured tofit within the shell (step 518).

Referring to FIG. 23, a flowchart of a process 520 for selling a mobilephone is shown, according to an exemplary embodiment. Process 520 isshown to include the steps of offering to sell a hardware customizablemobile phone with one or more selectable hardware components configuredto fit within a shell (step 522), offering a plurality of selectableoptions for at least one hardware component configured to fit within theshell (step 524), and receiving a selection of at least one hardwarecomponent configured to fit within the shell (step 532). Process 520 mayalso include one or more of the steps of offering a plurality ofselectable options for at least one hardware component configured to fitwithin the shell based on manufacturing complexity (step 526), offeringa plurality of selectable options for at least one hardware componentconfigured to fit within the shell based on availability of the hardwarecomponent (step 528), and offering a plurality of selectable options forat least one hardware component configured to fit within the shell basedon a rating of the hardware component (step 530).

Referring to FIG. 24, a flowchart of a process 600 for customizinghardware for a mobile phone is shown, according to an exemplaryembodiment. Process 600 is shown to include the steps of receiving froman end-user a selection of a mobile phone shell from a set of mobilephone shells (step 602), sending to the end-user a subset ofinterchangeable hardware components having different functions, thesubset of interchangeable hardware components generated based on acompatibility between the selected mobile phone shell and the set ofavailable interchangeable hardware components (step 604), and receivingfrom the end-user a selection of at least one hardware component fromthe subset of interchangeable hardware components (step 606).

Referring to FIG. 25, a flowchart of a process 610 for customizinghardware for a mobile phone is shown, according to an exemplaryembodiment. Process 610 is shown to include the steps of receiving overa computer network from an end-user a selection of a mobile phone shellfrom a set of mobile phone shells (step 612), sending over a computernetwork to the end-user a subset of interchangeable hardware componentshaving different functions, the subset of interchangeable hardwarecomponents generated based on a compatibility between the selectedmobile phone shell and the set of available interchangeable hardwarecomponents (step 620), and receiving over a computer network from theend-user a selection of at least one hardware component from the subsetof interchangeable hardware components (step 622). The process 610 mayalso include the steps of receiving over a computer network from theend-user a weight preference information (step 614), receiving over acomputer network from the end-user a cost preference information (step616), and receiving over a computer network from the end-user aselection of a preconfigured mobile phone from the set of mobile phoneshells, the preconfigured mobile phone including at least one emptyportion configured to receive an interchangeable hardware component(step 618).

It is also important to note that the construction and arrangement ofthe systems and methods as shown in the exemplary embodiments areillustrative only. Although only a few embodiments have been describedin detail, those skilled in the art who review this disclosure willreadily appreciate that many modifications are possible (e.g.,variations in sizes, dimensions, structures, shapes and proportions ofthe various elements, values of parameters, mounting arrangements, useof materials, colors, orientations, etc.) without materially departingfrom the novel teachings and advantages of the subject matter recited.For example, elements shown as integrally formed may be constructed ofmultiple parts or elements. It should be noted that the elements andassemblies disclosed herein may be constructed from any of a widevariety of materials that provide sufficient strength or durability, inany of a wide variety of colors, textures, and combinations.Additionally, in the subject description, the word “exemplary” is usedto mean serving as an example, instance or illustration. Any embodimentor design described herein as “exemplary” is not necessarily to beconstrued as preferred or advantageous over other embodiments ordesigns. Rather, use of the word exemplary is intended to presentconcepts in a concrete manner. Accordingly, all such modifications areintended to be included within the scope of the present inventions. Theorder or sequence of any process or method steps may be varied orre-sequenced according to alternative embodiments. Other substitutions,modifications, changes, and omissions may be made in the design,operating conditions, and arrangement of the preferred and otherexemplary embodiments without departing from scope of the presentdisclosure or from the scope of the appended claims.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure may be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media can be anyavailable media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Wheninformation is transferred or provided over a network or anothercommunications connection (either hardwired, wireless, or a combinationof hardwired or wireless) to a machine, the machine properly views theconnection as a machine-readable medium. Thus, any such connection isproperly termed a machine-readable medium. Combinations of the above arealso included within the scope of machine-readable media.Machine-executable instructions include, for example, instructions anddata which cause a general purpose computer, special purpose computer,or special purpose processing machines to perform a certain function orgroup of functions.

Although the figures may show a specific order of method steps, theorder of the steps may differ from what is depicted. Also two or moresteps may be performed concurrently or with partial concurrence. Suchvariation will depend on the software and hardware systems chosen and ondesigner choice. All such variations are within the scope of thedisclosure. Likewise, software implementations could be accomplishedwith standard programming techniques with rule based logic and otherlogic to accomplish the various connection steps, processing steps,comparison steps and decision steps.

What is claimed is:
 1. A mobile communication device comprising: aplatform having a generally rigid structure and including more than onehardware component receivers; the more than one hardware componentreceivers each configured to removably receive and electrically couplewith a respective interchangeable hardware module selected from at leasttwo interchangeable hardware modules; and processing electronicsincluding a bus and configured to communicatively couple with aninterchangeable hardware module removably received and electricallycoupled with a respective hardware component receiver of each of themore than one hardware component receivers, wherein the more than onehardware component receivers and the processing electronics have a busmodular architecture allowing the number and locations ofinterchangeable hardware modules respectively electrically coupled withthe more than one hardware component receivers to vary.
 2. The mobilecommunication device of claim 1, wherein the platform, the more than onehardware component receivers, and the processing electronics comply withan interchangeability standard.
 3. The mobile communication device ofclaim 2, wherein the interchangeability standard includes (i) a form orfit configuration providing the removable receiving between a hardwarecomponent receiver and an interchangeable hardware module, (ii) adimensional or structural configuration providing the electricallycoupling between a hardware component receiver and an interchangeablehardware module, and (iii) a protocol for communicating between theprocessing electronics and an interchangeable hardware module.
 4. Themobile communication device of claim 1, wherein the at least twointerchangeable hardware modules include at least two interchangeablecomputing hardware modules, each of the at least two interchangeablecomputing hardware modules respectively include processing electronics.5. The mobile communication device of claim 4, wherein the processingelectronics include a memory and a processor.
 6. The mobilecommunication device of claim 4, wherein the processing electronicsinclude a memory and a processor configured to electronically interactwith another interchangeable hardware module selected from the at leasttwo interchangeable hardware modules and communicatively coupled usingthe communications module.
 7. The mobile communication device of claim4, wherein the processing electronics include one or moremicroprocessors, an application specific integrated circuit (ASIC), acircuit containing one or more processing components, a group ofdistributed processing components, circuitry for supporting amicroprocessor, or other hardware configured for digital processing. 8.The mobile communication device of claim 1, further including anantenna, and wherein the antenna and the processing electronics arefurther configured to communicate with a wireless network.
 9. The mobilecommunication device of claim 1, wherein a first hardware componentreceiver of the more than one hardware component receivers includes afirst dimensional or structural configuration allowing it to removablyreceive and electrically couple with one of a first group of the atleast two interchangeable hardware modules but not with one of a secondgroup of the at least two interchangeable hardware modules, and a secondhardware component receiver of the more than one hardware componentreceivers includes a second dimensional or structural configurationallowing it to removably receive and electrically couple with one of thesecond group of interchangeable hardware modules but not with one of thefirst group of interchangeable hardware modules.
 10. The mobilecommunication device of claim 9, wherein the first dimensional orstructural configuration of the first hardware component receiverincludes a standardized first dimensional configuration.
 11. The mobilecommunication device of claim 9, wherein the second dimensional orstructural configuration of the second hardware component receiverincludes a standardized second dimensional configuration.
 12. The mobilecommunication device of claim 9, wherein the first hardware componentreceiver is a member of a first group of at least two hardware componentreceivers each having a substantially same size.
 13. The mobilecommunication device of claim 9, wherein two first hardware componentreceivers of the first group of at least two hardware componentreceivers are located adjacent on a surface of the platform.
 14. Themobile communication device of claim 13, where the two adjacent firsthardware component receivers are configured to respectively receive onethird interchangeable hardware module having a third dimensional orstructural configuration providing a removably receiving andelectrically coupling with the two adjacent first hardware componentreceivers, wherein the third interchangeable hardware module is selectedfrom at least two interchangeable third hardware modules havingdifferent functions.
 15. The mobile communication device of claim 9,wherein the mobile communication device is configured such that anotherfirst interchangeable hardware module selected from the at least twofirst interchangeable hardware modules may be interchanged with thefirst interchangeable hardware module.
 16. The mobile communicationdevice of claim 9, wherein the first interchangeable hardware module isselected by an end user.
 17. The mobile communication device of claim 9,wherein the mobile communication device includes a mobile cellulartelephone.
 18. The mobile communication device of claim 9, wherein theplatform is configured to be grasped by a human user.
 19. The mobilecommunication device of claim 1, wherein the platform, the more than onehardware component receivers, and the processing electronics include abus modular architecture allowing the number and locations of theinterchangeable hardware modules electronically coupled the at least twohardware module receivers to vary.
 20. The mobile communication deviceof claim 1, wherein the processing electronics include a communicationmodule.
 21. A mobile phone platform comprising: a first side having afirst side hardware module receiver configured to electronically couplewith a display hardware module and including a mechanism configured torespectively engage the display hardware module and resist removal ofthe display hardware module from the first side hardware modulereceiver; a second side having at least two second side hardware modulereceivers, the at least two second side hardware module receivers eachconfigured to respectively electronically couple with an interchangeablehardware module and including a mechanism configured to engage ahardware module and resist removal of the hardware module from thesecond side hardware module receiver; and processing electronicsincluding a bus and configured to communicatively couple with (i) thedisplay hardware module electronically coupled with the first sidehardware module receiver and (ii) a respective interchangeable hardwaremodule removably received and electrically coupled with a hardwaremodule receiver of at least two second side hardware module receivers,wherein the first side hardware module receiver, the at least two secondside hardware module receivers and the processing electronics have a busmodular architecture allowing the number and locations ofinterchangeable hardware modules electrically respectively coupled withthe hardware module receivers to vary.
 22. The mobile phone of claim 21,wherein the display hardware module includes an interchangeable displayhardware module.
 23. The mobile phone of claim 21, wherein theelectronic coupling includes electronically coupled to a commoncommunications bus associated with the platform.
 24. The mobile phone ofclaim 21, wherein the mechanism configured to engage a hardware moduleincludes a snap-in mechanism configured to engage the interchangeablehardware module and forcibly resist removal of the hardware module. 25.The mobile phone of claim 21, wherein the first side includes a majorside of the platform.
 26. The mobile phone of claim 21, wherein thesecond side includes a major side of the platform.
 27. The mobile phoneof claim 21, wherein the hardware module receivers comply with aninterchangeability standard.
 28. The mobile phone of claim 21, whereinthe processing electronics further include a memory and a processorconfigured to electronically interact with a respective interchangeablehardware module electrically coupled with a second side hardware modulereceiver of the at least two second side hardware module receivers. 29.The mobile phone of claim 21, wherein the processing electronics includea microprocessor, an application specific integrated circuit (ASIC), acircuit containing one or more processing components, a group ofdistributed processing components, circuitry for supporting amicroprocessor, or other hardware configured for digital processing. 30.The mobile phone of claim 21, wherein the mobile phone platform, theprocessing electronics, and the first side and second side hardwaremodule receivers comply with an interchangeability standard.
 31. Themobile phone of claim 21, wherein the mechanism of the at least twosecond side hardware module receivers is configured to engage a hardwaremodule and forcibly resist removal of the hardware module from thehardware module receiver.
 32. A mobile communication device comprising:a platform including at least two hardware component receivers locatedon a side of the platform; the at least two hardware component receiverseach configured to removably receive and electrically couple with arespective interchangeable hardware module selected from at least twointerchangeable hardware modules; and processing electronics including abus and configured to communicate with an interchangeable hardwaremodule removably received and electrically coupled with a respectivehardware component receiver of each of the at least two hardwarecomponent receivers, wherein the platform, the at least two hardwarecomponent receivers, and the processing electronics have a bus modulararchitecture allowing the number and locations of the interchangeablehardware modules electronically coupled with the at least two hardwarecomponent receivers to vary.
 33. The mobile communication device ofclaim 32, wherein the platform includes a platform having a generallyrigid structure.
 34. The mobile communication device of claim 32,wherein the platform includes a platform having a generally rectangularparallelepiped shape.
 35. The mobile communication device of claim 32,wherein the at least two hardware component receivers are located on asurface of the side of the platform.
 36. The mobile communication deviceof claim 32, wherein the platform has a handheld device form factor. 37.The mobile communication device of claim 32, wherein the platform has amobile device form factor.
 38. The mobile communication device of claim32, wherein the at least two hardware component receivers and the atleast two interchangeable hardware modules comply with aninterchangeability standard.
 39. The mobile communication device ofclaim 38, wherein the interchangeability standard includes (i) a form orfit configuration providing the removable receiving between a hardwarecomponent receiver and an interchangeable hardware module, (ii) adimensional or structural configuration providing the electricallycoupling between a hardware component receiver and an interchangeablehardware module, and (iii) a protocol for communicating between theprocessing electronics and an interchangeable hardware module.
 40. Themobile communication device of claim 32, wherein the at least twointerchangeable hardware modules respectively include processingelectronics.
 41. The mobile communication device of claim 32, whereinthe at least two interchangeable hardware modules each have a differentfunctionality.
 42. The mobile communication device of claim 32, whereinthe processing electronics further includes a bus configured tocommunicate with each interchangeable hardware module removably receivedand electrically coupled with a respective hardware component receiverof each of the at least two hardware component receivers.
 43. The mobilecommunication device of claim 32, further including an antenna, andwherein the antenna and the processing electronics are furtherconfigured to communicate with a wireless network.
 44. The mobilecommunication device of claim 32, wherein the mobile communicationdevice includes a mobile cellular telephone.
 45. The mobilecommunication device of claim 32, wherein the platform includes arectangular parallelepiped shaped platform.